An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

Hi everyone, My first app, Sort Rush: Package Factory (Apple ID: 6823296215), has been in "Waiting for Review" since October 17, 2026, and during this time I've made several attempts to move it forward: I replied to the "Guideline 2.1 - Information Needed - New App Submission" message on the same day, with a screen recording from a physical iPhone and all the requested information I submitted an expedited review request I used the Contact Us form to ask about the status (Case ID: 103005195582) Unfortunately, the status hasn't changed. I haven't cancelled or resubmitted the build, so I don't lose my place in the queue. The app is a simple offline puzzle game, rated 4+: no login, no user-generated content, no in-app purchases, only optional rewarded ads. I understand that new developer accounts need additional verification, but I'm not sure if anything else is needed from my side. I would really appreciate any help or suggestions on how to move the review forward. Thank you!

Hi, Our critical bug fix update for HungryAliens (App ID: 6449141384) has been stuck in the App Review process for 13 days since the initial rejection, with no further review progress. We addressed the rejection reason within approximately two hours, but the review did not resume. As a result, we submitted a new build on October 19. However, the new build has also remained in "Waiting for Review" status for 7 days, with no review initiated. We would like to request that an Apple reviewer check the current status and expedite the review process. If anyone has experienced a similar situation or knows of an official escalation path, your advice would also be greatly appreciated. Timeline September 15: Launched Guild Conquest, a large-scale competitive multiplayer feature. October 13: Bug fix update rejected under Guideline 1.1 (screenshot issue) → Corrected the screenshot and requested a re-review within approximately two hours. October 19: Withdrew the previous submission and submitted a new build after the review failed to resume. October 20: Posted an expedited review request on the Apple Developer Forums. October 26: The new build is still in "Waiting for Review" status, with no official response received. Why This Is Urgent Our large-scale multiplayer feature is currently experiencing critical issues, including a bug that prevents players from defeating a specific boss and issues with player information display. These issues are affecting normal gameplay progression and competitive fairness for many active players. Questions Is it normal for a new build to remain in the review queue for this long after a previous submission was rejected? If Apple Developer Support does not respond, is there an official escalation path or a way to request further assistance? These ongoing issues are affecting our active players and may lead to player churn, so we urgently need to deliver the necessary bug fixes. A response from an Apple reviewer or anyone who has navigated a similar situation would be greatly appreciated. Thank you.

Hello Apple App Review Team and Community, We would like to request an expedited review of a critical bug fix update for HungryAliens (App ID: 6449141384), which is currently live on the App Store. Our large-scale competitive multiplayer feature, Guild Conquest, launched on September 15, is experiencing critical issues, including a bug that prevents players from defeating a boss. These issues are directly affecting active players and disrupting normal gameplay progression. On October 13, our update was rejected due to an issue with an App Store screenshot. We corrected the screenshot and requested a re-review within approximately two hours. However, the review did not resume, so we withdrew the original submission and submitted a new build on October 19. The latest submission remains in "Waiting for Review" status, preventing us from delivering the necessary critical fixes to our players. App Information App Name: HungryAliens App ID: 6449141384 App Bundle ID: com.DetailGames.HungryAliens Timeline September 15: Launched Guild Conquest, a major competitive multiplayer feature. October 13: The update containing critical bug fixes for Guild Conquest was undergoing App Review. October 13: Received a rejection under Guideline 1.1 (Safety – Objectionable Content) related to an App Store screenshot → Corrected the screenshot and submitted the revised material through App Store Connect within approximately two hours, requesting the review to resume. October 13–19: Despite our prompt response, the review did not resume, delaying approval of the critical bug fix update. October 19: Withdrew the previous submission and resubmitted a build containing the necessary fixes. October 20: The latest submission remains in "Waiting for Review" status. Why This Is Urgent Guild Conquest is a large-scale competitive multiplayer feature involving many players, where accurate information display is essential. However, issues affecting this functionality are currently occurring. A critical bug is preventing players from defeating a specific boss in Guild Conquest, disrupting normal gameplay progression. These issues directly affect the gameplay experience and competitive fairness of players currently participating in the content. Although we promptly addressed the review feedback on October 13, the update has still not been approved, preventing us from delivering the necessary bug fixes. What We Are Requesting Expedited review of our October 19 submission, considering the critical gameplay issues affecting our live service. Confirmation of the current review status. Guidance on any additional information or actions required from our side. We understand and respect Apple's App Review Guidelines and review process, and we have made every effort to respond promptly to the feedback provided. We apologize for the urgent request and would sincerely appreciate your assistance in reviewing this critical bug fix update as soon as possible. Thank you for your time. We look forward to your response.

Waiting on a new app to be reviewed, we were approved for a Card Program go live, last Tuesday, but app hadn't been reviewed, we now are approved any locked in for the 3rd Nov. How do we get a new app reviewed, inline with Digital Card Program? Re-submitted last Tuesday at 1:21 PM after no activity Apple ID: 6759777960 Case ID: 103003281154

Hey, 14th Oct, I submitted an app with a digital card program, it got approved for the card program go live... but app wasn't reviewed. Tried a rebuild, resubmit, yet still not reviewed. We are approved to go live 3rd Nov for the card program, would love a review ASAP so we have time to resolve and resubmit any issues.

Hello, Our iOS app TAC FC: Football Manager (Apple ID 6817989550), version 1.0.2, was submitted on 10 October 2026 and has been in "Waiting for Review" ever since. It has never moved to "In Review". The macOS build of the same version was submitted one minute later and was reviewed and approved. We have requested an expedited review and messaged App Review (case 102996820289), but the iOS submission has not moved. Could someone from App Review please check whether this submission is stuck, or tell us if anything is missing? Thank you.

Our iOS app has been sitting in "In Review" for four weeks and we have not been able to get a status update through any channel, so I'm posting here in case someone from App Review can take a look. App: Epocra, iOS, version 1.0, build 268 Apple ID: 6813697639 Status: In Review since September 24, as Developer Support confirmed on October 1 Timeline Sept 22: build 267 rejected under 2.1(a), a launch crash on iPad Air running iPadOS 27. Fixed the same day and resubmitted as build 268. Sept 22: a reviewer signed in to the demo account that evening. No activity since. Sept 28: opened a status request through Contact Us, case 102979044954. On Oct 1 Developer Support replied that the review was "outside of our normal timeframe" and that the review team had been notified. Nothing since. Oct 5: second status request, case 102986888342. Acknowledgement only. Oct 9: replied in the App Review message thread for the submission citing both cases. No response. We have not changed anything on the submission while it is in review so we don't reset the queue. The app is a business phone app (CallKit and PushKit VoIP with server-side call recording and a consent screen on first launch). The review notes include a demo account, a walkthrough video, and a phone number the reviewer can call to test inbound calls. Is there anything else we should be doing to get this looked at, or can someone from App Review check on it? Happy to provide anything that would help.

I wanted to submit my first app to the App Store. I uploaded it, and the status changed to "Waiting for Review." It’s been over a week now, and the status hasn’t changed at all. Can anyone tell me what’s going on with the Apple team? Why are the reviews taking so long, especially since it says that 90% of apps are reviewed within 48 hours? Could it have something to do with the launch of the new "iPhone Duo"?)) Thanks a lot, everyone!

Hi, I submitted an app about 72-84 hours ago and I'm still waiting on it to get to the "In-Review" stage. I just requested an expedited review around hour 32, and I would really appreciate if anyone could shed some light on this. Is there a backlog or something?

Hello Apple App Review Team, I'm seeking urgent assistance with an App Store submission associated with App ID 6818598848. The updated submission has remained in Waiting for Review since October 14. An expedited review request has already been submitted, and we have contacted the available support channels, but the review has not yet started. Due to an important, time-sensitive launch deadline, this delay is becoming critical. Could an App Review team member please help confirm that the submission is correctly queued and advise whether any further action is required from our side? Additional information: I have already opened a case with Apple Developer Support regarding this prolonged delay and have submitted an expedited review request. Case ID: 102993879117 Thank you for your time and assistance.

Our first app, Best Tailgate (iOS 1.0.0 build 2, Submission ID 04736616-91b2-4277-840d-849912a93853), received a Guideline 2.1 Information Needed request on Oct 8. We replied on Oct 12 with every item requested, including a screen recording from a physical device, and resubmitted the same day. The submission has shown "Waiting for Review" since Oct 12 (13 days). Expedited review was approved on Oct 20 and again on Oct 21, and Developer Support case 103004366296 is open, but there is no reply box in App Store Connect and no further message from App Review. Could App Review please check this submission and let us know if anything else is needed from us? Thank you.

Hello App team, Please respond and assist. i have paid for the Developer program but if my app doesn't go into production, it will be a useless app after November as it is a Christmas APP. Our app, XmasMaps, has been stuck in "Waiting for Review" since October 14, 2026 (Submission ID: 5f1bb173-1f5d-40b5-a67a-2078db01f541). Timeline of previous actions: Sept 29, 2026: Initial submission Oct 8 & Oct 11, 2026: Resubmitted fixes following rejections Oct 14, 2026: new build resubmitted, currently stuck in "Waiting for Review" Oct 16, 2026: Expedited review request submitted Oct 19, 2026: Support customer inquiry submitted Android is already live, and we are hoping to clear iOS review so users can access the platform ahead of the upcoming holiday season. Oct 24, 2026: Rejected again for something already built into my latest build. i resubmitted right away and now put back into "waiting for review" when I would expect that the engineer who rejected it would take it back and finalize my app. Submission ID: 5f1bb173-1f5d-40b5-a67a-2078db01f541 Support Case ID: 102982950152 Team ID: 34WAQXFJHP I ask, please assist and review my app. It is already live on Google and i really need it live on both platforms to promote it. Could you please let me know if any additional information is needed from my side? I have paid the Developer fee of $99 per year and putting my own money for this Christmas App. Please! I beg for assistance to finally approve my app. Thank you.

Hi everyone, I submitted my app for App Review on August 14, 2026, at 2:39 PM. I later submitted an updated version again on September 9, 2026. The latest submission has been showing “In Review” for the past 5 days, but I still haven’t received any review decision or additional information from the App Review team. As I understand it, once an app enters the “In Review” status, a review decision is generally provided after the review is completed. However, in my case, the status has remained unchanged for several days. Has anyone experienced a similar situation recently? Is it normal for an app to remain in “In Review” for this long, or is there anything I should do from my side? Any advice or guidance would be appreciated. Thank you!

Hey Apple Developer Relations, App Review Team, and anyone else reading this,I wanted to share what’s been going on with my app because I’m honestly stuck and not sure what else to do.I’m an indie developer working on Marque: Car Collection — my first iOS app. I paid for the Developer Program, spent a lot of time getting everything ready, fixed the issues from the previous rejection, and submitted a new build.It’s been over a week now and I still have no idea what’s happening with it.Quick timeline: Oct 6: My previous submission got rejected under Guideline 5.1.2(i) (App Tracking Transparency). Oct 14: I submitted a fixed build, version 1.1.0 (24), with an updated ATT implementation, revised App Privacy details, and detailed notes explaining the changes. Since then (11 days as of Oct 25): It’s been sitting in “Waiting for Review” and hasn’t even moved to “In Review.” I’ve contacted Developer Support and asked on the forums, but I haven’t gotten any real answers. No one has asked for more information, explained what’s going on, or given me any idea when the review might actually start.I get that reviews can take longer sometimes, especially with a first app, subscriptions, or privacy-related stuff. I’m not asking anyone to just approve it without looking at it.What bothers me is the complete lack of communication. Right now I have no way of knowing: whether my build is just waiting in the normal queue or if something’s wrong with it when I can realistically plan a launch if there’s any point in contacting support again since I haven’t gotten a useful response so far I’m still paying for the Developer Program, but I have zero visibility into what’s happening with my submission.Apple holds developers to high standards. It would be nice to get at least basic transparency in return.So I have a few straightforward questions: Why has my corrected build been stuck in “Waiting for Review” for 11 days? Is there any way to confirm it’s properly in the queue and not stuck because of some technical or admin issue? Why hasn’t my support request gotten a real response? Is there an escalation path for indie developers when a submission just sits there with no explanation? If Apple can’t provide a status update, what options do developers have when they’re paying for the program but can’t get any information about their release? I’d really appreciate it if someone from Developer Relations or App Review could take a look and give me some kind of explanation (or point me to someone who can).I’d also be interested to hear from other developers who’ve dealt with similar long waits in “Waiting for Review,” especially with first apps.The issue isn’t just that the review is taking longer than expected. It’s that when something seems off, there’s almost no way to figure out what’s actually going on.Indie developers put a lot of time, money, and effort into building for Apple’s ecosystem. Clear communication shouldn’t be this hard.Thanks for reading. Marque Development Team

I am looking for guidance from Apple or other developers who have experienced a similar Guideline 4.3(a) rejection. I submitted an independently developed iPhone/iPad application, Canvasz AI: Passport ID Photo, for App Review. On September 30, 2026, the app was rejected under Guideline 4.3(a) – Design – Spam, with a general statement that the app appeared to share a similar binary, metadata, and/or concept with apps submitted by other developers. The problem is that I have not been able to determine what Apple actually considers similar. Canvasz AI was developed independently and was not created from a purchased template, white-label application, cloned application, or repackaged source code. The application includes product-specific functionality such as: Real-time face-position and distance guidance before taking a photo On-device face detection and format-aware automatic framing Passport/document head-size framing logic On-device background segmentation, matting, and replacement without uploading the user's photo to a processing server One source photo converted into multiple destination classes, including passport/visa/ID photos, profile images, social-media formats, and banners Batch generation/export of supported formats from one source photo An enhancement pipeline intended to preserve facial detail rather than apply a generic beauty filter Seven localized languages iPhone and iPad layouts Portrait and landscape support No account or signup requirement Core photo processing that works locally/on-device Following the rejection, I replied through App Store Connect asking whether the concern related specifically to: Binary/source-code similarity Metadata Visual assets/UI The application concept itself I also performed an additional source-provenance and similarity audit. The audit documented progressive source-control history and compared Canvasz AI against my other independently developed applications. It found no byte-identical application-specific source/assets across the compared applications, the common files identified were normal Flutter/iOS/Android generated framework/scaffolding files. I attached the forensic technical clarification report to App Review and offered to provide source-control history, architecture information, screenshots, development evidence, or additional technical information if required. I first replied on September 30 and followed up again on October 5. I still did not receive clarification identifying the actual similarity concern. I subsequently resubmitted the application on October 12, 2026, with detailed App Review notes and the forensic report attached. As of October 25, 2026, both the app and its in-app purchase remain Waiting for Review. I understand that App Review may require additional time, especially after a previous Guideline 4.3 rejection. I am not asking for special treatment or asking Apple to disclose another developer's confidential application or internal detection systems. What I need is enough actionable information to understand how to comply. Apple's published Guideline 4.3 states that apps in established categories may be accepted when they provide a meaningfully different or improved experience. I therefore have three specific questions: If an independently developed application receives a 4.3(a) rejection referring to "binary, metadata, and/or concept," how can the developer determine which of those dimensions actually caused the rejection? If source provenance and independent development evidence are provided, but no clarification is received, what additional evidence is normally useful for demonstrating that an application is not a template, clone, or repackaged application? For the "meaningfully different or improved experience" standard, should differentiation be evaluated on the complete user workflow and experience, or is overlap in individual features sufficient to trigger Guideline 4.3? I have invested significant development, testing, localization, and product-design effort into building a genuine application intended to provide useful functionality to users. I fully respect Apple's need to prevent spam, cloned apps, white-label applications, and low-effort template submissions. I support that objective. However, without knowing whether the concern is source code, metadata, UI/assets, or the concept itself, it is extremely difficult for an independent developer to make a meaningful correction instead of making speculative changes. I would appreciate guidance from Apple or developers who have encountered this situation and successfully obtained actionable clarification. Thank you.

Hello App Review Team, Our app has remained in "Waiting for Review" since 10/07 (with a resubmission on 10/20 after we cancelled to include the subscriptions), and we have not received a response through the available support channels. We had submitted an expedited review request, which was approved. The same app has already passed TestFlight external beta review, so we were not expecting the App Store review itself to take this long. It would be great to know if anything further is needed from us so that we can plan the launch accordingly. App details: Submission ID: f9633cec-c596-4e78-90b8-aec89b0e2691 Submitted: Oct 20, 2026 at 11:47 PM Current status: Waiting for Review Beta review: approved Thank you very much for your time.

Hi there, I'd appreciate if someone could look into the case of FloorLens (id 6762080790) being stuck "Waiting for review" for a minor but critical bugfix release. I even requested an expedited review 3 days ago which was accepted but there's absolutely no activity. This is especially weird as the prior major update was accepted in a record breaking 2.5 hours after submission (!). I'm wondering if 'Developer rejecting' an app while it's 'Waiting for review' carries some kind of penalty as I developer rejected this one twice to replace the build version early on? Best, Beren

Hello Apple Developer Support / App Review Team, My first iOS app, **PlanB: Dating, Social & Plans**, has remained in Waiting for Review since **October 13, 2026**. Submission ID: **28c83367-dd0b-4a22-b244-149277121d0d** The submission includes the iOS app version and associated in-app purchases and subscriptions. All submitted items continue to show Waiting for Review as of October 23, 2026. I have already submitted an expedited review request through the official portal and raised a support ticket, but I have not received any response or any indication that the review has started. This **delay is blocking the planned launch of my app** which is planned on 27Oct. I understand that review timelines can vary, and I am ready to provide any additional information or resolve any issues immediately. Could you please: - Confirm whether my expedited review request has been received and considered. - Confirm whether any information, agreement, or other requirement is preventing the review from starting. - Escalate the submission for review or advise me on the appropriate next step. I would appreciate any clarification on the status of this submission. Regards, PlanB Developer

Is anyone else feeling deeply disappointed by the lack of communication around App Review? I submitted my iOS app on October 6. As of October 24, it is still “Waiting for Review” — approximately 18 days later. I contacted Apple Developer Support on October 13 and followed up on October 22. So far, I have received no response explaining what is happening, whether anything is wrong with my submission, or whether I need to take any action. For reference, here are the details of my submission: App ID: 6817446637 Platform / Version: iOS / 1.0.0 Submitted: October 6, 2026, at 14:18 JST (UTC+9) Current status: Waiting for Review Support case: 102995107676 Reading other threads here, I have seen developers describing similar experiences: prolonged waits, unanswered inquiries, and no clear indication of what to do next. Seeing those reports makes this situation even more discouraging. I understand that review times vary and that some apps require additional checks. I do not expect an annual membership fee to guarantee approval or priority treatment. But we pay an annual fee to participate in the Apple Developer Program, and I think it is reasonable to expect basic communication and a meaningful response when something appears to be stuck. Waiting more than two weeks without review starting is frustrating enough. Having no response to a support inquiry after 11 days makes it much worse. Even a brief explanation that the case is being investigated, or an indication of when to expect an update, would make a difference. As an independent developer who has put considerable time and effort into building an app, this experience has been deeply disappointing. In my view, this level of communication is not acceptable for a paid developer program. For others who have been in this situation, did you eventually receive a response or find a way to get the issue investigated? Was there a specific support channel that actually helped? If Apple staff are reading this, I hope you will take these experiences seriously. Developers should not have to post publicly just to find out whether their submissions and support requests are being handled.

My app and subscription products are in Waiting for review since Oct 15th. Has anyone get it resolved? I've got Business 3.0.0 preamble error and an automated message asked to confirm the price of in-app purchases, i've confirmed the price, updated the review and resubmitted it. The preamble error is gone from the distribution page but the app is in waiting for review since Oct 15th. No additional replies in thread. Contacted support on Oct 22nd, No response till now. Is this normal? The app's launch is getting delayed because of this.